home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: Re(2): FW_CODPart::WritePartInfo
- Sent: 7/19/96 4:55 PM
- Received: 7/22/96 10:48 AM
- From: Hutchings, Richard B. "Brad", brad@hutchings-software.com
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- > Making the file smaller would require moving content around in a
- > potentially expensive process. This is essentially a stop-and-copy
- > garbage collection. The user can initiate this kind of file compression
- > by saving a draft in a new file, where the new file will be compact and
- > the old file can be discarded if desired.
- >
- > This rewrite operation might sound like a reasonable default behavior to
- > occur every time the file is saved, but the bigger the file gets, then
- > the longer the copying takes and the greater amount of RAM and/or disk is
- > consumed, potentially exhausting them before the operation completes. It
- > seems user unfriendly to engage in very expensive operations without
- > receiving explicit instructions to do so.
-
- One way the user can compact files is to "Save As...". This gives the
- desired results, i.e. a compacted file. However, OpenDoc does not allow the
- user to save over the current file.
-
- Here's what would be a useful user/developer tool. Write a simple droplet
- script application that opens a file, saves it as a temporary file, deletes
- the original file, and replaces it with the renamed temporary. Problem
- solved.
-
- I wonder if there isn't a way that root parts could do a similar thing.
-
- Brad
-
- <mailto: "Brad Hutchings" brad@hutchings-software.com>
- <http://www.hutchings-software.com>
-
- Ask me about:
- Hutchings Software's Rapid-I(tm) Button
- Hutchings Software's Essential Strips(tm)
-
-
-